Processor with debug pipeline

ABSTRACT

A processor includes an execution pipeline that includes a plurality of execution stages, execution pipeline control logic, and a debug system. The execution pipeline control logic is configured to control flow of an instruction through the execution stages. The debug system includes a debug pipeline and debug pipeline control logic. The debug pipeline includes a plurality of debug stages. Each debug pipeline stage corresponds to an execution pipeline stage, and the total number of debug stages corresponds to the total number of execution stages. The debug pipeline control logic is coupled to the execution pipeline control logic. The debug pipeline control logic is configured to control flow through the debug stages of debug information associated with the instruction, and to advance the debug information into a next of the debug stages in correspondence with the execution pipeline control logic advancing the instruction into a corresponding stage of the execution pipeline.

CROSS REFERENCE TO RELATED APPLICATION(S)

This application is a continuation of U.S. patent application Ser. No. 15/200,900, filed on Jul. 1, 2016, which claims priority to U.S. patent application Ser. No. 14/255,055, filed Apr. 7, 2014 and now U.S. Pat. No. 9,384,109, which are hereby incorporated by reference.

BACKGROUND

Embedded software development and debugging using processors, such as microcontrollers, can be challenging. Accordingly, many processors include on-chip debug features to facilitate the software development process. Among the most fundamental debug features are program breakpoints. Program breakpoints allow the processor to be halted when software execution reaches a specific address. Once the processor is halted, a debug tool can examine the state of system memory and registers in the processor by issuing instructions to be executed on the processor through a debug protocol. Once the examination is completed, the debug tool can return the CPU to normal mode, and execution will continue until the next breakpoint. Some processors include circuitry to facilitate use of breakpoints. Such “hardware breakpoints” are non-intrusive, and have virtually no impact on software execution until the breakpoint triggers.

SUMMARY

A system and method for providing debugging in a processor with reduced energy consumption are disclosed herein. In one embodiment, a processor includes an execution pipeline, execution pipeline control logic, and a debug system. The execution pipeline includes a plurality of execution stages. The execution pipeline control logic is configured to control flow of an instruction through the execution stages. The debug system includes a debug pipeline and debug pipeline control logic. The debug pipeline includes a plurality of debug stages. Each of the debug pipeline stages corresponds to one of the execution pipeline stages, and a total number of the debug stages corresponds to a total number of the execution stages. The debug pipeline control logic is coupled to the execution pipeline control logic. The debug pipeline control logic is configured to control flow through the debug stages of debug information associated with the instruction, and to advance the debug information into a next of the debug stages in correspondence with the execution pipeline control logic advancing the instruction into a corresponding stage of the execution pipeline.

In another embodiment, a method includes providing an instruction to an initial stage of an execution pipeline of a processor. Concurrently with the providing of the instruction, debug information is provided to a debug pipeline of the processor. The debug pipeline is distinct from the execution pipeline and includes a same number of stages as the execution pipeline. The debug information propagates through the debug pipeline simultaneously with propagation of the instruction through the execution pipeline. Execution of the instruction is halted based on the debug information propagating into a predetermined stage of the debug pipeline.

In a further embodiment, a processor includes an execution power domain, a debug power domain, a debug tool detection circuit, an execution pipeline, and a debug system. The debug tool detection circuit is configured to: detect whether a debug tool is connected to the processor, and to enable power to the debug power domain responsive to detecting the debug tool connected to the processor. The execution pipeline includes a plurality of instruction execution stages disposed in the execution power domain. The debug system is disposed in the debug power domain. The debug system includes a debug pipeline that includes a plurality of debug stages. Each of the debug pipeline stages corresponds to one of the instruction execution stages, and a total number of the debug stages corresponds to a total number of the instruction execution stages. The debug pipeline is configured to advance the debug information into a next of the debug stages in correspondence with the execution pipeline advancing an instruction corresponding to the debug information into the corresponding stage of the execution pipeline.

BRIEF DESCRIPTION OF THE DRAWINGS

For a detailed description of exemplary embodiments of the invention, reference will now be made to the accompanying drawings in which:

FIG. 1 shows a block diagram of a processor in accordance with various embodiments;

FIG. 2 shows a debug system in a processor in accordance with various embodiments; and

FIG. 3 shows a flow diagram for a method for debugging in accordance with various embodiments.

NOTATION AND NOMENCLATURE

Certain terms are used throughout the following description and claims to refer to particular system components. As one skilled in the art will appreciate, companies may refer to a component by different names. This document does not intend to distinguish between components that differ in name but not function. In the following discussion and in the claims, the terms “including” and “comprising” are used in an open-ended fashion, and thus should be interpreted to mean “including, but not limited to . . . .” Also, the term “couple” or “couples” is intended to mean either an indirect or direct electrical connection. Thus, if a first device couples to a second device, that connection may be through a direct electrical connection, or through an indirect electrical connection via other devices and connections. The recitation “based on” is intended to mean “based at least in part on.” Therefore, if X is based on Y, X may be based on Y and any number of additional factors.

DETAILED DESCRIPTION

The following discussion is directed to various embodiments of the invention. Although one or more of these embodiments may be preferred, the embodiments disclosed should not be interpreted, or otherwise used, as limiting the scope of the disclosure, including the claims. In addition, one skilled in the art will understand that the following description has broad application, and the discussion of any embodiment is meant only to be exemplary of that embodiment, and not intended to intimate that the scope of the disclosure, including the claims, is limited to that embodiment.

Processor on-chip debugging systems that include hardware breakpoints, watchpoints and the like require that the processor include circuitry dedicated to the breakpoints and other debugging functions. In conventional processor on-chip debugging circuitry, the processor execution pipeline includes circuitry that allows instruction breakpoint information to propagate through the pipeline with the instruction until the instruction reaches a specified pipeline stage and the breakpoint information is applied to halt instruction execution. Because this additional debug circuitry is integrated into the processor's execution pipeline, the circuitry consumes energy whenever the processor is executing instructions, regardless of whether software is being debugged, thereby reducing processor power efficiency.

Embodiments of the present disclosure provide on-chip debugging that includes hardware breakpoints and the like with reduced energy consumption. The processor disclosed herein provides a debug pipeline that is separate from the processor's execution pipeline. Breakpoint information for an instruction propagates through the debug pipeline in lock-step with the propagation of the instruction through the execution pipeline. Because the debug pipeline is separate from the execution pipeline, the debug pipeline and other processor on-chip debugging features need only be powered during a debugging session. Accordingly, embodiments of the processor include separate and independent execution and debug power domains. Components located in the debug power domain, such as the debug pipeline, debug address comparison logic, etc. are powered only during debugging, which reduces overall processor energy consumption in the vast majority of execution conditions, because software development time, during which debugging features are used, constitutes only a tiny fraction of overall processor operation time.

FIG. 1 shows a block diagram of a processor 100 in accordance with various embodiments. The processor 100 may be a general purpose microprocessor, a digital signal processor, a microcontroller, or other computing device that executes instructions retrieved from an instruction memory. The processor 100 includes execution logic 102 and a debug system 104. The execution logic 102 includes circuitry that executes instructions retrieved from memory. The debug system 104 is coupled to the execution logic 102. The debug system 104 includes logic that controls execution of instructions in the execution logic 102 to allow for debugging of instructions being executed by the execution logic 102. For example, the debug system 104 may halt execution of instructions by the execution logic 102 if the execution logic 102 executes an instruction retrieved from a particular memory address. Signals 110 exchanged by the execution logic 102 and the debug system 104 are applied to synchronize the operation of the execution logic and the debug system 104.

The processor 100 includes an execution power domain 106 and a debug power domain 108. The execution logic 102 is disposed in the execution power domain 106. The debug system 104 is disposed in the debug power domain 108. The debug power domain 108 is separate and distinct from the execution power domain 106. The execution power domain 106 is an area of the processor 100 that provides power to the execution logic 102 to allow the execution of instructions. Accordingly, the execution power domain 106 provides power whenever instructions are to be executed (e.g., when power is provided to the processor 100). The debug power domain 108 is an area of the processor 100 that provides power to the debug system 104 to allow debugging of an instruction stream being executed by the execution logic 102. The debug power domain 108 provides power only while the debug system 104 is being used to debug an instruction stream executed by the execution logic 102. Because the debug power domain 108 provides power to the debug system 104 only while debugging, the processor 100 uses less energy than a processor that includes debugging circuitry that is powered whenever the processor and/or the execution logic is powered. The processor 100 provides the debugging capabilities of a conventional processor while consuming less energy than a conventional processor because the debug system 104 is only powered while debugging.

FIG. 2 shows the processor debug system 104 and other subsystems of the processor 100 in greater detail. The execution logic 102 includes an execution pipeline 202 and execution pipeline control logic 210. The debug system 104 includes a debug pipeline 214, debug pipeline control logic 212, comparators 222 and registers 224. The processor 100 also includes debug tool detection circuitry 228 and debug power circuitry 230.

The execution pipeline 202 includes a plurality of execution stages 204, 206, 208 that incrementally execute an instruction. For example, the execution pipeline 202 may include a fetch stage 204, a decode stage 206, and an execute stage 208. Other embodiments may include different execution stages and/or a different number of execution stages.

The fetch stage 204 retrieves instructions from instruction memory for execution by the processor 100. The instruction memory is a storage device, such as a random access memory (volatile or non-volatile) that stores instructions to be executed. The instruction memory may an internal component of the processor 100, or alternatively may be external to the processor 100. The fetch stage 204 provides the retrieved instructions to the decode stage 206.

The decode stage 206 examines the instructions received from the fetch stage 204, and translates each instruction into controls suitable for operating the execute stage 208, processor registers, and other components of the processor 100 to perform operations that effectuate the instructions. The decode stage 206 provides control signals to the execute stage 208 that cause the execute stage 208 to carry out the operations needed to execute each instruction.

The execute stage 208 includes arithmetic circuitry, shifters, multipliers, registers, logical operation circuitry, etc. that are arranged to manipulate data values as specified by the control signals generated by the decode stage 206. Some embodiments of the processor 100 may include multiple execution pipelines 202 that provide the same or different data manipulation capabilities.

The execution control logic 210 controls the propagation of instructions through the execution stages of the execution pipeline 202. For example, if execution of a given instruction in the execute stage 208 requires a particular number of clock cycles, the execution control logic 210 may advance instructions in the execution pipeline 202 on expiration of the particular number of clock cycles.

The debug pipeline 214 includes a plurality of debug stages 216, 218, 220. The debug stages propagate debug information through the debug pipeline 214. The debug pipeline 214 has the same number of debug stages as the execution pipeline 202 has execution stages. Debug information in the debug pipeline 214 advances through the debug pipeline 214 in synchronization with the advancement of an instruction corresponding to the debug information through the execution pipeline 202.

The debug pipeline control logic 212 controls the propagation of the debug information through the stages 216-220 of the debug pipeline 214. The debug pipeline control logic 212 is coupled to the execution pipeline control logic 210. Signals 110 provided to the debug pipeline control logic 212 by the execution pipeline control logic 210 indicate when an instruction is propagating from stage to stage of the execution pipeline 212. Responsive to the signals 110, the debug pipeline control logic 212 causes debug information to advance through the debug pipeline 214 in lock-step with advancement of the instruction corresponding to the debug information through the execution pipeline 202. For example, when an instruction is retrieved into the fetch stage 204, debug information corresponding to the instruction is loaded into the debug stage 216. When the instruction advances from the fetch stage 204 to the decode stage 206, the debug information advances from debug stage 216 to debug stage 218. Similarly, when the instruction advances from the decode stage 206 to the execute stage 208, the debug information advances from debug stage 218 to debug stage 220. Advancement through the debug pipeline stages 216-220 is synchronized with advancement of the instruction through the execution pipeline stages 204-208 by the signals 110 provided to the debug pipeline control logic 212 by the execution pipeline control logic 210.

The registers 224 store memory addresses of instructions and/or data being used in debugging. For example, an instruction address stored in a selected register 224 may be a breakpoint address used to halt instruction execution in the execution pipeline 202 when an instruction at the address in the selected register 224 is executed, decoded, fetched, etc. Similarly, an address stored in a selected register 224 may be a watchpoint address used to halt instruction execution in the execution pipeline 202 when the address in the selected register 224 is accessed for reading or writing.

The registers 224 are coupled to the comparators 222. The comparators 222 compare the address values stored in the registers 224 to the instruction addresses driven onto the instruction bus 232 by the fetch stage 204. The instruction bus 232 conveys instructions and instruction addresses between instruction memory and the fetch stage 204. The output of comparators 222 is included in the debug information loaded into the debug pipeline 214 and propagated through the stages 216-220. When debug information indicating a positive address comparison propagates into a selected stage of the debug pipeline 214, the debug pipeline control logic 212 notifies the execution pipeline control logic 210, via signals 110, and the execution pipeline control logic 210 can halt execution of instructions in the execution pipeline 202.

The registers 236 store values of data used in debugging. For example, a data value stored in a selected register 236 may be used to halt instruction execution in the execution pipeline 202 when the data value is output by the execute stage 208.

The registers 236 are coupled to the comparators 234. The comparators 234 compare the data values stored in the registers 236 to the data values driven onto the data bus by the execution pipeline 202. The output of comparators 234 may be provided to a debug pipeline stage 216-220 corresponding to the execution pipeline stage 204-208 that performed the transaction associated with the data value. For example, if the execute stage 208 drives a data value onto the data bus for storage in a register of the processor 100, the output of the comparators 234 may be provided to debug pipeline stage 220.

Some embodiments of the processor 100 may include multiple instances of the execution pipeline 202, or a portion thereof. Such embodiments may include an instance of the debug pipeline 214 coupled to each instance of the execution pipeline 202 to provide debugging services with regard to instructions executing in the execution pipeline 202.

As explained above, the debug system 104 is powered only while software is being debugged. In some embodiments, the processor 100 detects whether a debug tool is connected to the processor 100, and controls provision of power to the debug system 104 based on whether a debug tool is connected to the processor 100. The debug tool detection circuitry 228 detects whether a debug tool is connected to the processor 100. The debug tool detection circuitry 228 may detect connection of a debug tool to the processor 100 by identifying a clock signal generated by the debug tool and provided to the processor 100. In other embodiments, the debug tool detection circuitry 228 may detect connection of a debug tool by a different method. The debug tool detection circuitry 228 provides a signal indicating whether a debug tool is connected to the processor 100 to the debug power circuitry 230. The debug power circuitry 230 switches power to the debug system 104 (i.e., the debug power domain 108) when the debug tool detection circuitry 228 indicates that a debug tool is connected to the processor 100, and disconnects power from the debug power system 104 when the debug tool detection circuitry 228 indicates that the debug tool is not connected to the processor 100. An execution power system powers the execution logic 102 independently of the debug system 104.

FIG. 3 shows a flow diagram for a method 300 for debugging in a processor in accordance with various embodiments. Though depicted sequentially as a matter of convenience, at least some of the actions shown can be performed in a different order and/or performed in parallel. Additionally, some embodiments may perform only some of the actions shown.

In block 302, the processor 100 is powered, the execution logic 102 is powered, and the debug system 104 is not powered because a debug tool is not connected to the processor 100. The debug tool detection circuitry 228 is monitoring a debug tool port of the processor 100 to determine whether a debug tool is connected to the processor 100.

In block 304, the debug tool detection circuitry 228 detects connection of a debug tool to the processor 100, and in response to detection of connection of the debug tool, power is switched to the debug system 104 and the debug system 104 is enabled to provide debugging functionality.

In block 306, the processor 100 is executing instructions. As an instruction is loaded into the execution pipeline 202 to be executed in block 306, debug information corresponding to the instruction is loaded into the debug pipeline 214 in block 308. The debug information may indicate whether an address of the instruction or of data accessed by the instruction corresponds to an address stored in the registers 224.

In block 310, the debug information is propagated through the debug pipeline 214 in synchronization with propagation of the corresponding instruction through the execution pipeline 202.

In block 312, the processor 100 applies the debug information in the debug pipeline 214 to control instruction execution in the execution pipeline 202. For example, propagation of the debug information to a given stage of the debug pipeline 214 may halt execution of instructions in the execution pipeline 202.

In block 314, the debug tool detection circuitry 228 is monitoring the debug tool port of the processor 100, and determines that the debug tool has been disconnected from the processor 100.

In block 316, responsive to detection of the disconnection of the debug tool, power is disconnected from the debug system 104. Power to the execution logic 102 is independent of power to the debug system 104. Accordingly, when power is disconnected from the debug system 104, the execution logic 102 remains powered and may execute instructions while the debug system 104 is unpowered.

The above discussion is meant to be illustrative of the principles and various embodiments of the present invention. Numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications. 

What is claimed is:
 1. An electronic device comprising: an input/output (I/O) port; a processor that includes: an execution sub-system that includes an execution pipeline; and a debug sub-system that includes a debug pipeline; power circuitry that includes: a first power domain to supply power to the execution pipeline; and a second power domain to supply power to the debug sub-system; and detection circuitry to detect a connection an external debug tool to the I/O port; wherein the power circuitry causes the second power domain to supply power to the debug sub-system upon detection of the connection of the external debug tool to the I/O port and to otherwise prevent the second power domain from supplying power to the debug sub-system.
 2. The electronic device of claim 1, wherein the connection of the external debug tool to the I/O port is detectable by the detection circuitry as a clock signal generated in response to the connection of the external debug tool to the I/O port.
 3. The electronic device of claim 1, wherein, when the second power domain is currently supplying power to the debug sub-system in response the connection of the external debug tool to the I/O port, the power circuitry causes the second power domain to stop supplying power to the debug sub-system in response to the detection circuitry detecting a disconnection of the external debug tool from the I/O port.
 4. The electronic device of claim 1, wherein the first and second power domains are separate from each other and are independently controllable by the power circuitry.
 5. The electronic device of claim 1, wherein the debug sub-system includes debug power circuitry to power the debug pipeline, and wherein the second power domain supplies power to the debug sub-system by powering on the debug power circuitry.
 6. The electronic device of claim 1, wherein the execution pipeline includes a plurality of execution stages, and wherein the execution sub-system includes execution control logic to control a flow of a first instruction through the execution stages.
 7. The electronic device of claim 6, wherein the debug pipeline includes a plurality of debug stages equal in number to the plurality of execution stages, and wherein each debug stage corresponds to a respective one of the execution stages.
 8. The electronic device of claim 7, wherein the debug sub-system further includes debug control logic to control flow through the debug stages of debug information associated with the first instruction and to advance the debug information through each debug stage in synchronization with advancement of the first instruction through each respective execution stage.
 9. The electronic device of claim 8, wherein the debug information comprises at least one of breakpoint information or watchpoint information.
 10. The electronic device of claim 8, further comprising: an instruction memory; and an input bus coupled to an input of the execution pipeline to provide instruction information to a first stage of the execution pipeline, the instruction information including the first instruction and an instruction address of the first instruction in the instruction memory; wherein the debug sub-system further includes: a first register to store an address value; and a first comparator coupled to the input bus and to the first register and arranged to receive the instruction address from the input bus, receive the address value from the first register, and output a first comparison result of the instruction address and the address value to the debug pipeline; wherein, when the comparison result indicates a match between the instruction address and the address value, the debug control logic signals the execution control logic to halt execution of the first instruction in the execution pipeline.
 11. The electronic device of claim 10, wherein the debug sub-system further includes: a second register to store a data value; and a second comparator coupled to an output of the execution pipeline and arranged to output a second comparison result of the data value and the output of the execution pipeline to the debug stage corresponding to the execution stage that generated the output of the execution pipeline.
 12. A method for operating an electronic device having a power system that includes separate first and second power domains, the method comprising: supplying power to an execution sub-system of a processor of the electronic device using the first power domain; and supplying power to a debug sub-system of the processor using the second power domain upon detecting that an external debug tool is connected to an input/output (I/O) port of the electronic device and otherwise preventing power from being supplied to the debug sub-system.
 13. The method of claim 12, wherein detecting that the external debug tool is connected to the I/O port includes detecting a clock signal generated by the external debug tool.
 14. The method of claim 12, wherein, when currently supplying power to the debug sub-system using the second power domain in response the connection of the external debug tool to the I/O port, stopping the supply of power to the to the debug sub-system using the second power domain upon detecting that the external debug tool is removed from the I/O port.
 15. The method of claim 12, further comprising, when power is being supplied to the execution sub-system by the first power domain and to the debug sub-system by the second power domain, advancing an instruction through each of a plurality of execution stages of an execution pipeline of the execution sub-system in lock-step with advancing debug information corresponding to the instruction through each of a plurality of debug stages of a debug pipeline of the debug sub-system, wherein the plurality of execution stages is equal in number to the plurality of debug stages and each execution stage corresponds to a respective one of the debug stages. 